Message categorization

ABSTRACT

One or more techniques and/or systems are provided for defining a message behavior profile for a sender, which may be used to categorize messages from the sender. A message behavior profile may be defined based upon, for example, message distribution behavior of the sender (e.g., volume, frequency, variance in content amongst messages sent to recipients, etc.); recipient interactions with messages from the sender (e.g., message read rates, message response rates, etc.); unsubscription options comprised within messages from the sender; and/or other factors. In this way, the message behavior profile and/or features extracted from a message may be used to categorize a message from the sender (e.g., newsletter, commercial advertisements, alert, social network etc.). Categorized messages may be organized into folders, displayed or hidden within views, and/or processed based upon their respective categorizations.

BACKGROUND

Today, many individuals and commercial entities utilize electroniccommunication mediums for communication. For example, users maycommunicate through instant message applications, email, text messages,etc. Communication messages may be sent for a variety of purposes, suchas personal messages, newsletters, commercial advertisements, socialnetwork messages, job alerts, and/or a plethora of other purposes.Unfortunately, a user's experience with electronic communication may bediminished because the user may be overwhelmed with large quantities ofmessages. For example, a user's email inbox may be inundated withhundreds of emails a week that the user may or may not have the timeand/or interest in reading. Thus, the user may inadvertently overlookinteresting emails while attempting to sift through their email inbox.Current techniques may allow a user to manually setup rules to placemessage into folders created by the user. Unfortunately, many users maynot take advantage of message processing rules because of the complexityinvolved in setting up such rules. Other techniques may provide spamfilters that specifically target spam messages. However, such techniquesmay not detect, categorize, and/or organize other types of messages.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key factors oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter.

Among other things, one or more systems and/or techniques for defining amessage behavior profile for categorizing messages are disclosed herein.A message behavior profile may be defined for a sender based upon avariety of observed features associated with the sender, recipients,message content, interactions between the sender and recipients, and/orother behavioral features (e.g., message sending patterns, howrecipients react to messages, etc.). The message behavior profile may beindicative of the type of messages the sender may send (e.g., the sendermay have a tendency to send spam, personal messages, job alerts, socialnetwork updates, newsletters, commercial messages, etc.). In this way,the message behavior profile and/or other information (e.g., featuresextracted from a current message) may be used to categorize messagesfrom the sender in advance and/or in real-time. Additionally, messagesbehavior profiles may be associated with senders based upon IP address,an IP address range, sending domain, an unsubscription email address, asession initiation protocol address, a DNS server, a user account, adigital certificate (e.g., DKIM, PGP, digital certificate signer), aphone number, etc. Thus, a sender may be identified with particularityeven though the sender may have multiple and/or ambiguous sender emailaddresses (e.g., a spammer may attempt to conceal the spammer's identityby hiding behind multiple email addresses from a single IP address).

In one example of defining a message behavior profile, one or moremessage read rates may be specified within the message behavior profile.A message read rate may correspond to a number of messages from thesender read by a recipient compared to (e.g., ratio) a number ofmessages received (by that recipient) from the sender (e.g., if arecipient reads messages of the sender at a high frequency, then suchmessages of the sender may be deemed personal; if a recipient rarelyreads message of the sender (but reads messages from other senders),then such messages of the sender may be deemed non-personal; etc.). Inanother example of defining the message behavior profile, one or moremessage response rates may be specified within the message behaviorprofile. A message response rate may correspond to a number ofrecipients that responded, replied, saved, forwarded, etc. a messagesent by the sender, for example. Accordingly, as used herein responserate and/or the like is not intended to be limited to actuallyresponding to (the sender of) a message, but may also comprise otheractions as well (e.g., that are not directly responsive (to thesender)), such as saving, forwarding and/or editing, etc., for example.In another example of defining a message behavior profile, one or moremessage distribution patterns may be specified within the messagebehavior profile. It may be appreciated that a message distributionpattern may correspond to various message volume patterns, sendingfrequency patterns, and/or other patterns. For example, a messagedistribution pattern may correspond to a number of distinct messagessent by the sender to recipients (e.g., a message campaign of the sendermay indicate that the sender distributes similar messages to a largenumber of recipients at similar times, which may indicate that thesender has a tendency to send bulk non-personalized newsletters torecipients).

It may be appreciated that a variety of other features may be specifiedwithin the message behavior profile. In one example, an unsubscriptionfeature may be specified within the message behavior profile. Theunsubscription feature may correspond to a number of messages comprisingan unsubscription option sent by the sender (e.g., if a sender sendsmessages with an unsubscription features above a predeterminedthreshold, then the unsubscription features may indicate that the senderhas a tendency to send newsletters and/or commercial advertisements torecipients). In another example, a message variance feature may bespecified within the message behavior profile. The message variancefeature may be specified by computing a fuzzy signature for one or moremessages associated with the sender. For example, hash values may becomputed from message content, such that messages that differ slightlymay result in similar hash values, whereas messages with differentcontent may result in different hash values. The message variancefeature may be indicative of message content variance across messagessent by the sender (e.g., dissimilar hash values may indicate that thesender may have a tendency to send unique personalized messages, such aspersonal emails, whereas similar hash values may indicate that thesender has a tendency to send similar messages, such as newsletters,etc, that merely comprise a different “to” or “addressee” entry, forexample).

It may be appreciated that a variety of sender behavior patterns may beleveraged when defining the message behavior profile. For example, thetiming of when and/or how the sender sends messages may be used todetermine the type of messages the sender may have a tendency to send.In one example, the sender may send a burst of messages to a pluralityof recipients at a similar time, which may indicate that the messagesare newsletters as opposed to personal messages. In another example, thesender may send messages at regular intervals (e.g., Monday mornings),which may indicate the messages are newsletters as opposed to personalmessages. In another example, variance in the number of messagesreceived across recipients may be used to define the message behaviorprofile. It may be appreciated that other sender behavior patterns maybe used to define the message behavior profile, and that merely a fewexamples are set forth and that the claimed subject matter is not meantto be limited to merely the examples set forth herein.

In this way, the message behavior profile may be defined for the sender.The message behavior profile may be indicative of the type of messagessent by the sender. Thus, the message behavior profile may be utilizedin categorizing messages from the sender. Categorizing messages mayenhance a user's communication experience by grouping similar categoriesof messages into folders, providing message viewing panels tailored forvarious categorizes of messages and/or applying particular rules and/oractions to messages based upon their category (e.g., a clean-up policymay remove newsletter messages from an inbox after 10 days, but does notaffect other categories of messages), etc. It may be appreciated that amessage may be categorized regardless of whether a message behaviorprofile exits for a sender. For example, a message may be categorized inreal-time (e.g., upon receipt of the email, but before delivery of theemail into a recipient inbox) based upon features extracted from themessage (e.g., metadata and/or message content such as a URL,advertisement, image, HTML structure, text, download link, etc.). If amessage behavior profile exists, then the extracted features may be usedto supplement the categorization of a message from the sender. If amessage behavior does not exist, then the extracted features may be usedto categorize the message.

To the accomplishment of the foregoing and related ends, the followingdescription and annexed drawings set forth certain illustrative aspectsand implementations. These are indicative of but a few of the variousways in which one or more aspects may be employed. Other aspects,advantages, and novel features of the disclosure will become apparentfrom the following detailed description when considered in conjunctionwith the annexed drawings.

DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flow chart illustrating an exemplary method of defining amessage behavior profile for a sender.

FIG. 2 is a flow chart illustrating an exemplary method of categorizingmessages.

FIG. 3 is a component block diagram illustrating an exemplary system fordefining a message behavior profile for a sender.

FIG. 4 is an illustration of an example of message behavior profile fora sender.

FIG. 5 is an illustration of an example of organizing messages intofolders within a message frontend based upon categories of the messages.

FIG. 6 is an illustration of an example of presenting messages within aview of a message frontend based upon categories of the messages.

FIG. 7 is an illustration of an exemplary computer-readable mediumwherein processor-executable instructions configured to embody one ormore of the provisions set forth herein may be comprised.

FIG. 8 illustrates an exemplary computing environment wherein one ormore of the provisions set forth herein may be implemented.

DETAILED DESCRIPTION

The claimed subject matter is now described with reference to thedrawings, wherein like reference numerals are generally used to refer tolike elements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the claimed subject matter. It may beevident, however, that the claimed subject matter may be practicedwithout these specific details. In other instances, structures anddevices are illustrated in block diagram form in order to facilitatedescribing the claimed subject matter.

Many users of electronic communication mediums are inundated withmessages on a daily basis. For example, a user may engage in numeroustext message and/or instant message conversations a day. In addition,the user may also receive hundreds of email messages a week.Unfortunately, the user may not have the time, resources, and/or desireto sift through hundreds of messages to locate interesting messages. Forexample, a user may have a high interest in personal emails and socialnetwork updates; a medium interest in certain newsletters, commercialadvertisements, and alerts; and a low interest in other newsletters andcommercial advertisements that were not specifically subscribed to bythe user; and zero interest in spam. The user may receive a plethora ofmessages spanning the range of uninteresting to highly interesting.Because the user may receive a large volume of messages, many of theinteresting messages may be overlooked amongst the uninterestingmessages. Current solutions may allow a user to customize messagedelivery manually. In particular, the user may direct messages from aspecific sender to folder separate from a user inbox. However, suchsolutions merely take into account the specific sender defined withinthe message processing rule, and may not attempt to intelligentlyprocess messages from other undefined senders. In particular, currentmessage processing solutions may not attempt to intelligently processmessages from undefined senders based upon behavior patterns of thesender (e.g., if a sender sends similar emails in bulk at similar times,then the sender may be sending non-personal newsletters; if the sendersends dissimilar messages infrequently, the sender may be sendingpersonal messages; etc.). Additionally, current message processingsolutions may not take into account recipient behavior (e.g., if amajority of recipients read messages from the sender, then the sendermay be sending interesting messages; if a majority of recipients respondto messages from the sender, then the sender may be sending personalmessages; etc.).

Accordingly, one or more systems and/or techniques for defining amessage behavior profile that may be used for categorizing messages aredisclosed herein. In particular, sender behavior patterns, recipientinteraction patterns, and/or other features may be used to define amessage behavior profile for a sender. The message behavior profile maybe indicative of the categories/types of messages sent by the sender(e.g., a distribution of probabilities indicating likelihoods thatmessages of a sender correspond to various categories; a single overallcategory corresponding to messages of the sender; etc.). The messagebehavior profile and/or features extracted from a message may be used tocategorize the message from the sender. In this way, a user's experiencewith a message user interface may be enhanced by providing additionalfeatures and/or options based upon categories of messages. For example,messages from a sender may be categorized as newsletters based upon amessage behavior profile of the sender, and thus may be placed into aparticular folder, displayed within a particular view, and/or processedin accordance with message processing polices defined for newsletters.

One embodiment of defining a message behavior profile is illustrated byan exemplary method 100 in FIG. 1. At 102, the method starts. At 104,one or more message read rates may be specified within a messagebehavior profile for a sender. A message read rate may correspond to anumber of messages from the sender read by recipients compared with anumber of messages received (by the recipients) from the sender (e.g., anumber of messages from a sender read by the recipient over a predefinedtime period; a number of messages from the sender read by the recipientcompared with a total number of messages received from the sender over apredefined time period; etc.).

In one example of a message read rate, a recipient may read a percentageof messages from the sender above a predetermined threshold (e.g., therecipient may read 60% of messages received from the sender). Suchrecipient behavior may indicate that messages from the sender areinteresting (e.g., personal messages, social network updates, onlinebill payment notifications, desired job alerts, etc.). In anotherexample of a message read rate, a recipient may read a percentage ofmessages from the sender below a predetermined threshold (e.g., therecipient may read less than 15% of messages received from the sender).Such recipient behavior may indicate that messages from the sender arenot interesting (e.g., unsolicited newsletters, commercialadvertisements, etc.). It may be appreciated that other recipientbehaviors corresponding to message read rates may be indicative of awide variety of message categories, and that merely a few examples areset forth and that the claimed subject matter is not meant to be limitedto merely the examples set forth herein.

At 106, one or more message response rates may be specified within themessage behavior profile. A message response rate may correspond to anumber of recipients that responded, replied, forwarded, saved, etc. amessage sent by the sender. In one example of a message response rate,recipients may read messages from a sender above a predeterminedthreshold (e.g., above 15%), but may respond to the sender below apredetermined threshold (e.g., below 5%). Such a recipient behavior mayindicate that messages from the sender are newsletters, commercialadvertisements, job alerts, social network updates, etc., as opposed topersonal emails, which may generally lend themselves to conversationscomprising back and forth message communication with a higher responserate (e.g., above 50%). It may be appreciated that other recipientbehaviors corresponding to message response rates (e.g., a messageresponse rate based upon a rate at which messages from the sender areforwarded to other users; a message response rate based upon a time spanbetween receipt of a message and an action taken upon the message, suchas deletion, reply, forward, save, etc.; a message response rate basedupon actions taken upon message from the sender, such as deletion,reply, forward, save, etc.; etc.) may be indicative of a wide variety ofmessage categories, and that merely a few examples are set forth.Accordingly, response rate and/or the like as used herein, including asregards the scope of the appended claims, is not meant to be limited toa response or responses per se to one or more messages.

At 108, one or more message distribution patterns may be specifiedwithin the behavior profile. It may be appreciated that a messagedistribution pattern may related to a variety of patterns correspondingto how the sender sends messages (e.g., volume, frequency, similarity inmessage content, similarity in message send times, similarity in messagesend times across various recipients, average number of recipients formessages and/or a variety of other metrics and/or comparisons ofmetrics). For example, a message distribution pattern may correspond toa number of distinct messages sent by the sender to recipients. In oneexample of a message distribution pattern, a sender may send a number ofemails above a predetermined threshold (e.g., 20 similar emails that areemailed at one time to 20 recipients) at regular intervals (e.g., once aday). Such sender behavior may indicate that messages from the senderare newsletters, commercial advertisements, etc. It may be appreciatedthat other sender behaviors corresponding to message distributionpatterns may be indicative of a wide variety of message categories, andthat merely a few examples are set forth.

It may be appreciated that other features (e.g., features extracted froma message, variance in message content between messages sent to variousrecipients, etc.) may be taken into account when defining the messagebehavior profile. In one example of defining the message behaviorprofile, an unsubscription feature maybe specified within the messagebehavior profile. The unsubscription feature may correspond to a numberof messages comprising an unsubscription option (e.g., an unsubscribelink within an email) sent by the sender. If the unsubscription featureindicates that the sender sends messages with an unsubscription optionabove a predetermined threshold (e.g., 50% of messages comprise anunsubscription option), then the subscription feature may indicate thatthe sender has a tendency to send newsletters, commercialadvertisements, and/or other subscription based messages, as opposed topersonal messages, transaction messages (e.g., receipts), and/or othernon-subscription messages. It may be appreciated that an unsubscriptionfeature may be indicative of a wide variety of message categories, andthat merely a few non-limiting examples are set forth.

In another example of defining the message behavior profile, a messagevariance feature may be specified by computing a fuzzy signature for oneor more messages associated with the sender. The message variancefeature may be indicative of content variance across messages sent bythe sender (e.g., an amount of change in email content, such as text,between a first message sent to a first recipient and a second emailsent to a second recipient at a similar time). In one example, a fuzzysignature may be computed by calculating hash values from messagecontent for one or more messages. Messages with similar hash values maybe deemed to have similar content (e.g., message content may beduplicated between messages; message content may vary merely insalutations). If the sender sends messages with similar fuzzy signatures(e.g., messages with similar hash values) at similar times torecipients, then the fuzzy signatures may indicate that the sender has atendency to send newsletters, commercial advertisements, and/or othernon-personalized messages In contrast, if the sender sends messages withdifferent fuzzy signatures (e.g., messages with different hash values)at similar times to recipients, then the fuzzy signatures may indicatethat the sender has a tendency to send personalized emails, such asalerts.

It may be appreciated that one or more categories corresponding to thesender may be specified within the message behavior profile of thesender. The one or more categories (e.g., a single category, multiplecategories and/or a probability distribution of categories, etc.) may bebased upon message read rates, message response rates, messagedistribution patterns, unsubscription features, message variancefeatures and/or a variety of other features associated with the sender,messages from the sender, recipient interactions with messages from thesender and/or message content, etc. In this way, the message behaviorprofile may be used to categorize messages from the sender. For example,a message may be categorized in real-time before delivery of the messageso that additional processing may be performed on the message. Suchprocessing may enhance the recipient's experience with messagecommunication (e.g., newsletters may be placed into a newsletter folder,social network updates may be displayed or hidden based upon a viewsetting, and/or alert messages may be deleted after one week; etc.). At110, the method ends.

One embodiment of categorizing messages is illustrated by an exemplarymethod 200 in FIG. 2. At 202, the method starts. It may be appreciatedthat a message from a sender may be categorized based upon extractedfeatures/content of the message and/or a message behavior profile of thesender. The sender may be identified based upon an IP address, an IPaddress range, a from message address, a sending domain, an unsubscribeemail address, a session initiation protocol address, a DNS server, auser account, a digital certificate, a phone number and/or otheridentification. In this way, a sender, such as a spammer, may beidentified notwithstanding the sender using alternative sendingaddresses (e.g., in contrast to conventional techniques that may becircumvented by a nefarious sender that may “hide” behind different,rotating, etc. addresses). At 204, a message received by a recipientfrom a sender may be categorized into a category based upon a messagebehavior profile associated with the sender (e.g., the message may becategorized in real-time before delivery of the message to therecipient). The message behavior profile may correspond to message readrates, message response rates, and/or message distribution patterns. Amessage read rate within the message behavior profile may have beenspecified based upon prior interactions of recipients with messages fromthe sender (e.g., how often recipients read messages from the sender,how often recipients read messages from the sender compared with howoften the recipients read messages from other senders, etc.). A messageresponse rate within the message behavior profile may have beenspecified based upon prior interactions of recipients with messages fromthe sender (e.g., how often recipients responded, replied, forwarded,saved, etc. messages from the sender). A message distribution patternwithin the message behavior profile may have been specified based uponprior sending patterns of the sender (e.g., volume, frequency and/orother patterns of messages sent by the sender)

The message behavior profile may correspond to unsubscription features.An unsubscription feature within the message behavior profile may havebeen specified based upon a number of messages comprising anunsubscription option sent by the sender. It may be appreciated that anunsubscription feature parsed from the message received by the recipientfrom the sender may be used to categorize the message (e.g., the messagebehavior profile may indicate that the sender has a tendency to sendpersonal emails, however, the current email may comprise anunsubscription option that may be used to categorize the current emailas a newsletter).

The message behavior profile may correspond to message variancefeatures. A message variance feature specified within the messagebehavior profile may have been specified based upon fuzzy signatures ofone or more messages. The fuzzy signatures may be indicative of contentvariance across message sent by the sender (e.g., messages with similarfuzzy signatures, such as similar hash values, may be deemed to havesimilar message content, and thus may be deemed as non-personalizedmessages; message with dissimilar fuzzy signatures, such as dissimilarhash values, may be deemed to have dissimilar message content, and thusmay be deemed as personalized messages (e.g., particularly if they areread and/or responded to as well); etc.). It may be appreciated that afuzzy signature computed from the message received by the recipient maybe used to categorize the message (e.g., if the fuzzy signature issimilar to fuzzy signatures of other messages sent by the sender, thenthe message may be deemed as non-personalized).

The message behavior profile may comprise one or more categoriesspecified for the sender. That is, one or more categories may have beenspecified for the sender based upon message read rates, message responserates, message distribution patterns, unsubscription features, messagevariance features and/or a variety of other features and/or contentassociated with prior messages sent by the sender. In this way, messagesfrom the sender may be efficiently categorized using the one or morecategories specified for the sender within the message behavior profile(e.g., as opposed to performing a computationally intensive analysis ofthe message received by the recipient from the sender, a category may bequickly assigned to the message from the one or more categoriesspecified within the message behavior profile of the sender).

In some instances a message behavior profile may not exist for a sender,while in other instances a message behavior profile for a sender may bebased upon sparse and/or incomplete data (e.g., categorization data maybe based upon ten prior messages associated with a sender as opposed tocategorization data based upon thousands of prior messages). In oneexample, the message may be categorized based upon one or more features(e.g., URL, text, advertisements, images, HTML structure, downloadlinks, etc.) extracted from the message regardless of whether a messagebehavior profile exists for the sender. In another example, the messagemay be categorized based upon one or more features and/or contentextracted from the message in real-time if a message behavior profiledoes not exist for the sender.

In one example of categorizing the message using the message behaviorprofile, the sender of the message may be identified. The senderidentification may be used to locate (e.g., lookup within a messagebehavior profile database) the message behavior profile corresponding tothe sender. The message behavior profile may specify one or more messageread rates, one or more message response rates, one or more messagedistribution patterns and/or features specified for the sender. Suchfeatures may be used to categorize the message. For example, anaggregate of the one or more message read rates may indicate thatmessages of the sender are read by recipients below a predetermined readrate (e.g., 10% of messages from the sender are read by recipients). Anaggregate of the one or more message response rates may indicate thatmessages of the sender are responded to by recipients below apredetermined response rate (e.g., 4% of recipients reply, forward,and/or take other actions associated with messages from the recipient).An aggregate of one or more message distribution patterns may indicatethat the sender is a bulk message sender of similar messages sent atsimilar times (e.g., the sender typically sends about 500 messages withthe similar content (e.g., similar hash values) at the same or similartime(s) and/or the sender typically sends messages to a set of 500recipients at regular weekly intervals, etc.). In this way, the messagemay be categorized with a newsletter category and/or a commercialadvertisement category. It may be appreciated that additional features,such as unsubscription features, may be used when categorizing themessage. It may be appreciated that features and/or content extractedfrom the message may be used when categorizing the message.

In another example of categorizing the message using the messagebehavior profile, the sender of the message may be identified. Thesender identification may be used to locate the message behavior profilecorresponding to the sender. The message behavior profile may specifyone or more message response rates, one or more message distributionpatterns and/or other features specified for the sender. Such featuresmay be used to categorize the message. For example, an aggregate of theone or more message response rates may indicate that messages of thesender are responded to by recipients below a predetermined responserate (e.g., less than 10% of recipients reply to messages of thesender). An aggregate of the one or more message distribution patternsmay indicate that the sender is a bulk message sender of dissimilarmessages (e.g., the sender may typically send about 500 dissimilarmessages at similar times to recipients at regular weekly intervals,where the messages are personalized for the respective recipients). Inthis way, the message may be categorized with an alert category (e.g.,spam, job alert, bank statement alert, etc.).

An aggregate of one or more message distribution patterns may indicatethat messages from the sender vary in volume and frequency betweenrecipients above a predetermined variance threshold (e.g., the sendermay frequently send social network update messages to a first recipientbased upon the first recipient interacting with the social network on adaily basis, but may infrequently send social network update messages toa second recipient based upon that second recipient interacting with thesocial network a few times a week). In this way, the message may becategorized with a social network category. It may be appreciated thatadditional features, such as unsubscription features, may be used whencategorizing the message. It may be appreciated that features and/orcontent extracted from the message may be used when categorizing themessage.

It may be appreciated that categories with which a message does notmatch may be used to (indirectly) categorize the message (e.g., aprocess of elimination may be performed to categorize a message). Forexample, if an aggregate of message read rates of the sender are below apredetermined threshold, an aggregate of message response rates of thesender are below a predetermined threshold, and the message does notmatch an alert category, then the message may be categorized as anewsletter.

After categorization, the message may be processed and/or delivered intoa message user interface of the recipient (e.g., an email application; atext message application of a cell phone; etc.). In one example, themessage may be organized into a folder corresponding to the category ofthe message. In another example the message may be presented within aview corresponding to the category (e.g., the message may be displayedor hidden within an inbox of the message user interface based upon aview option selection). In another example, an action may be performedupon the message. The action may be associated with a user definedmessage processing policy corresponding to the category. For example,the user may specify a clean-up policy for a particular category ofmessages, such that messages assigned to the category may be deletedafter a user defined period of time. At 206, the method ends.

FIG. 3 illustrates an example of a system 300 configured for defining amessage behavior profile 306 for a sender. The system 300 may comprise aprofile component 304 and/or a categorization component 308. The profilecomponent 304 may define the message behavior profile 306 based uponprior message data within a message interaction database 302. Forexample, sender message distribution patterns, recipient interactpatterns, extracted message features and/or other message informationassociated with the sender may be used to define the message behaviorprofile 306.

The profile component 304 may be configured to specify one or moremessage read rates within the message behavior profile 306 for thesender. A message read rate may correspond to a number of messages fromthe sender read by recipients compared with a number of messagesreceived (by the recipients) from the sender. The profile component 304may be configured to specify one or more message response rates withinthe message behavior profile 306. A message response rate may correspondto a number of recipients that responded to a message sent by thesender. The profile component 304 may be configured to specify one ormore message distribution patterns. A message distribution pattern maycorrespond to a number of distinct messages sent by the sender torecipients. In one example, a message distribution pattern may indicatethat the sender has a tendency to send a large number, such as 500, ofmessages to recipients at the same time, where the messages comprisesimilar message content, and thus the sender may be deemed to sendnon-personalized newsletters and/or commercial advertisements. Inanother example, a message distribution pattern may indicate that thesender has a tendency to send a large number, such as 500, of messagesto recipients over a short time span, such as 1 minute, where themessages comprise dissimilar message content, and thus the sender may bedeemed to send personalized alerts.

The profile component 304 may be configured to specify other featureswithin the message behavior profile 306. For example, the profilecomponent 304 may specify an unsubscription feature within the messagebehavior profile 306. The unsubscription feature may correspond to anumber of messages comprising an unsubscription option sent by thesender. The profile component 304 may be configured to specify one ormore categories for the sender within the message behavior profile 306.The one or more categories may be indicative of the types of messagessent by the sender. In this way, messages from the sender may becategorized using the message behavior profile 306 and/or extractedfeatures from such messages.

The categorization component 308 may be configured to categorize amessage 310 from the sender into a category based upon the messagebehavior profile 306. The categorization component 308 may be associatedwith a message processing system 312. The message processing system 312may be configured to process messages for a message frontend 320 (e.g.,an email application). For example, the message processing system 312may receive and/or send messages for the message frontend 320. Themessage processing system 312 may receive the message 310. Thecategorization component 308 may extract message data (e.g., extractedmessage data 314) from the message. For example, the extracted messagedata 314 may comprise a sender identification and/or extracted featuresand/or content of the message. The categorization component 308 maydetermine that the message behavior profile 306 is associated with thesender based upon the sender identification. The categorizationcomponent 308 may determine a category 316 for the message 310 basedupon the message behavior profile 306 and/or the extracted features. Thecategorized message 318 may be processed and/or delivered to the messagefrontend 320. For example, the categorized message 318 may be organizedinto a particular folder and/or may be displayed or hidden within aninbox based upon the category of the message.

It may be appreciated that the categorization component 308 may beconfigured to categorize a message even though a message behaviorprofile may not exist for a sender of the message. In one example, thecategorization component 308 may be configured to categorize a messagefrom a second sender for which a message behavior profile does notexist. For example, the categorization component 308 may categorize themessage based upon features and/or extracted from the message.

FIG. 4 illustrates an example 400 of a message behavior profile 402 fora sender. The message behavior profile 402 may comprise a message readrate 404. For example, the message read rate 404 may indicate that 5% ofmessages sent by the sender are read by recipients. It may beappreciated that the message read rate 404 may be based upon otherfactors (e.g., a number of messages from the sender that are read byrecipients over a particular timespan, such as 3 days, compared with anumber of messages sent to the recipients by the sender over thatparticular (3 day) time span, etc.). The message behavior profile 402may comprise a message response rate 406. For example, the messageresponse rate 406 may indicate that 2% of messages sent by the senderare responded to by recipients. It may be appreciated that the messageresponse rate 406 may be based upon other factors (e.g., a percentage ofrecipients that reply to messages from the recipient, a percentage ofrecipients that forward messages from the recipient, communication (suchas a new message) from the recipient to the sender which may or may notbe associated with a message received (by the recipient) from thesender, etc.).

The message behavior profile 402 may comprise a message distributionpattern 408. For example, the message distribution pattern 408 mayindicate that 80% of messages sent by the sender are sent to more than20 recipients at a single time. The message behavior profile 402 maycomprise a message distribution pattern 410. For example, the messagedistribution pattern 410 may indicate that 60% of messages are sent withsimilar content during similar time frames to recipients. It may beappreciated that the message distribution pattern 408 and/or the messagedistribution pattern 410 may be based upon other factors (e.g., volume,frequency and/or other sending patterns).

The message behavior profile 402 may comprise a message variance feature412. For example, the message variance feature 412 may indicate that 75%of messages sent by the sender to multiple recipients may comprisesimilar content. It may be appreciated that the message variance feature412 may be based upon other features (e.g., fuzzy signatures, variancein message content amongst messages to a single recipient over time fromthe sender and/or variance in message content amongst messages tomultiple recipients sent at the same time, variance in volume and/ortime across recipients (e.g., a recipient receiving a large number ofmessages from a sender at irregular times compared with other recipientsmay indicate that the messages are social network updates), etc.). Themessage behavior profile 402 may comprise an unsubscription feature 414.For example, the unsubscription feature 414 may indicate that 92% ofmessages sent by the sender comprise an unsubscription option. Themessage behavior profile 402 may comprise a category 416. For example,the category 416 may indicate that there may be a 90% probability thatmessages sent by the sender may be newsletters. In this way, the messagebehavior profile may be used to categorize messages of the sender.

FIG. 5 illustrates an example 500 of organizing messages into folderswithin a message frontend 502 based upon categories of the messages. Auser may utilize the message frontend 502 for message communication. Forexample, the message frontend 502 may generally display messages for theuser within an inbox. Unfortunately, the inbox may be inundated with alarge number of emails that may or may not interest the user.Accordingly, messages may be categorized and organized intocorresponding folders. In one example, a garden club message from agarden club sender may be categorized as a newsletter based upon amessage behavior profile for the garden club sender. A car dealermessage from a car dealer sender may be categorized as a newsletterbased upon a message behavior profile for the car dealer sender. In thisway, the garden club message and/or the car dealer message may beorganized into a newsletters folder 504.

In another example, a job finder message from a job finder sender may becategorized as an alert based upon a message behavior profile for thejob finder sender. In this way, the job finder message may be organizedinto an alerts folder 506. In another example, a stay connected messagefrom a social network sender may be categorized as a social networkmessage based upon a message behavior profile for the social networksender. In this way, the stay connected message may be organized into asocial network folder 508. In another example, a work message from aboss sender may be categorized as a personal message based upon amessage behavior profile for the boss sender. A social message from afriend sender may be categorized as a personal message based upon amessage behavior profile for the friend sender. In this way, the workmessage and/or the social message may be organized into the inbox 510.

FIG. 6 illustrates an example 600 of presenting messages within a viewof a message frontend 602 based upon categories of the messages. A usermay utilize the message frontend 602 for message communication. Forexample, the message frontend 502 may generally display messages for theuser within an inbox. Unfortunately, the inbox may be inundated with alarge number of emails that may or may not interest the user.Accordingly, messages may be categorized and presented in correspondingviews (e.g., a view setting of an inbox, a separate viewing panel,etc.). In one example, the message frontend 602 may comprise a displaynewsletters button 604, a display social network button 606, a displayalerts button 608, and/or other display buttons. The display newslettersbutton 604 may be used to display or hide (e.g., filter) newslettermessages within an inbox of the message frontend 602 (e.g., a gardenclub newsletter and a car dealer newsletter are displayed within theinbox). The display social network button 606 may be used to display orhide social network messages within the inbox (e.g., a stay connectedmessage may be hidden within the inbox). The display alerts button 608may be used to display of hide alert messages within the inbox (e.g., ajob finder message may be hidden within the inbox). In this way, themessage frontend 602 may display categorized messages based upon userdesired display settings.

Still another embodiment involves a computer-readable medium comprisingprocessor-executable instructions configured to implement one or more ofthe techniques presented herein. An exemplary computer-readable mediumthat may be devised in these ways is illustrated in FIG. 7, wherein theimplementation 700 comprises a computer-readable medium 716 (e.g., aCD-R, DVD-R, or a platter of a hard disk drive), on which is encodedcomputer-readable data 714. This computer-readable data 714 in turncomprises a set of computer instructions 712 configured to operateaccording to one or more of the principles set forth herein. In one suchembodiment 700, the processor-executable computer instructions 712 maybe configured to perform a method 710, such as at least some of theexemplary method 100 of FIG. 1 and/or exemplary method 200 of FIG. 2,for example. In another such embodiment, the processor-executableinstructions 712 may be configured to implement a system, such as atleast some of the exemplary system 300 of FIG. 3, for example. Many suchcomputer-readable media may be devised by those of ordinary skill in theart that are configured to operate in accordance with the techniquespresented herein.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

As used in this application, the terms “component,” “module,” “system”,“interface”, and the like are generally intended to refer to acomputer-related entity, either hardware, a combination of hardware andsoftware, software, or software in execution. For example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration, both an application runningon a controller and the controller can be a component. One or morecomponents may reside within a process and/or thread of execution and acomponent may be localized on one computer and/or distributed betweentwo or more computers.

Furthermore, the claimed subject matter may be implemented as a method,apparatus, or article of manufacture using standard programming and/orengineering techniques to produce software, firmware, hardware, or anycombination thereof to control a computer to implement the disclosedsubject matter. The term “article of manufacture” as used herein isintended to encompass a computer program accessible from anycomputer-readable device, carrier, or media. Of course, those skilled inthe art will recognize many modifications may be made to thisconfiguration without departing from the scope or spirit of the claimedsubject matter.

It may be appreciated that at least one of A and B and/or the likegenerally means A or B or both A and B.

FIG. 8 and the following discussion provide a brief, general descriptionof a suitable computing environment to implement embodiments of one ormore of the provisions set forth herein. The operating environment ofFIG. 8 is only one example of a suitable operating environment and isnot intended to suggest any limitation as to the scope of use orfunctionality of the operating environment. Example computing devicesinclude, but are not limited to, personal computers, server computers,hand-held or laptop devices, mobile devices (such as mobile phones,Personal Digital Assistants (PDAs), media players, and the like),multiprocessor systems, consumer electronics, mini computers, mainframecomputers, distributed computing environments that include any of theabove systems or devices, and the like.

Although not required, embodiments are described in the general contextof “computer readable instructions” being executed by one or morecomputing devices. Computer readable instructions may be distributed viacomputer readable media (discussed below). Computer readableinstructions may be implemented as program modules, such as functions,objects, Application Programming Interfaces (APIs), data structures, andthe like, that perform particular tasks or implement particular abstractdata types. Typically, the functionality of the computer readableinstructions may be combined or distributed as desired in variousenvironments.

FIG. 8 illustrates an example of a system 810 comprising a computingdevice 812 configured to implement one or more embodiments providedherein. In one configuration, computing device 812 includes at least oneprocessing unit 816 and memory 818. Depending on the exact configurationand type of computing device, memory 818 may be volatile (such as RAM,for example), non-volatile (such as ROM, flash memory, etc., forexample) or some combination of the two. This configuration isillustrated in FIG. 8 by dashed line 814.

In other embodiments, device 812 may include additional features and/orfunctionality. For example, device 812 may also include additionalstorage (e.g., removable and/or non-removable) including, but notlimited to, magnetic storage, optical storage, and the like. Suchadditional storage is illustrated in FIG. 8 by storage 820. In oneembodiment, computer readable instructions to implement one or moreembodiments provided herein may be in storage 820. Storage 820 may alsostore other computer readable instructions to implement an operatingsystem, an application program, and the like. Computer readableinstructions may be loaded in memory 818 for execution by processingunit 816, for example.

The term “computer readable media” as used herein includes computerstorage media. Computer storage media includes volatile and nonvolatile,removable and non-removable media implemented in any method ortechnology for storage of information such as computer readableinstructions or other data. Memory 818 and storage 820 are examples ofcomputer storage media. Computer storage media includes, but is notlimited to, RAM, ROM, EEPROM, flash memory or other memory technology,CD-ROM, Digital Versatile Disks (DVDs) or other optical storage,magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, or any other medium which can be used to storethe desired information and which can be accessed by device 812. Anysuch computer storage media may be part of device 812.

Device 812 may also include communication connection(s) 826 that allowsdevice 812 to communicate with other devices. Communicationconnection(s) 826 may include, but is not limited to, a modem, a NetworkInterface Card (NIC), an integrated network interface, a radio frequencytransmitter/receiver, an infrared port, a USB connection, or otherinterfaces for connecting computing device 812 to other computingdevices. Communication connection(s) 826 may include a wired connectionor a wireless connection. Communication connection(s) 826 may transmitand/or receive communication media.

The term “computer readable media” may include communication media.Communication media typically embodies computer readable instructions orother data in a “modulated data signal” such as a carrier wave or othertransport mechanism and includes any information delivery media. Theterm “modulated data signal” may include a signal that has one or moreof its characteristics set or changed in such a manner as to encodeinformation in the signal.

Device 812 may include input device(s) 824 such as keyboard, mouse, pen,voice input device, touch input device, infrared cameras, video inputdevices, and/or any other input device. Output device(s) 822 such as oneor more displays, speakers, printers, and/or any other output device mayalso be included in device 812. Input device(s) 824 and output device(s)822 may be connected to device 812 via a wired connection, wirelessconnection, or any combination thereof. In one embodiment, an inputdevice or an output device from another computing device may be used asinput device(s) 824 or output device(s) 822 for computing device 812.

Components of computing device 812 may be connected by variousinterconnects, such as a bus. Such interconnects may include aPeripheral Component Interconnect (PCI), such as PCI Express, aUniversal Serial Bus (USB), firewire (IEEE 1384), an optical busstructure, and the like. In another embodiment, components of computingdevice 812 may be interconnected by a network. For example, memory 818may be comprised of multiple physical memory units located in differentphysical locations interconnected by a network.

Those skilled in the art will realize that storage devices utilized tostore computer readable instructions may be distributed across anetwork. For example, a computing device 830 accessible via a network828 may store computer readable instructions to implement one or moreembodiments provided herein. Computing device 812 may access computingdevice 830 and download a part or all of the computer readableinstructions for execution. Alternatively, computing device 812 maydownload pieces of the computer readable instructions, as needed, orsome instructions may be executed at computing device 812 and some atcomputing device 830.

Various operations of embodiments are provided herein. In oneembodiment, one or more of the operations described may constitutecomputer readable instructions stored on one or more computer readablemedia, which if executed by a computing device, will cause the computingdevice to perform the operations described. The order in which some orall of the operations are described should not be construed as to implythat these operations are necessarily order dependent. Alternativeordering will be appreciated by one skilled in the art having thebenefit of this description. Further, it will be understood that not alloperations are necessarily present in each embodiment provided herein.

Moreover, the word “exemplary” is used herein to mean serving as anexample, instance, or illustration. Any aspect or design describedherein as “exemplary” is not necessarily to be construed as advantageousover other aspects or designs. Rather, use of the word exemplary isintended to present concepts in a concrete fashion. As used in thisapplication, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or”. That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. In addition, the articles “a” and “an” as usedin this application and the appended claims may generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form. Also, at least one of A and B and/orthe like generally means A or B or both A and B.

Also, although the disclosure has been shown and described with respectto one or more implementations, equivalent alterations and modificationswill occur to others skilled in the art based upon a reading andunderstanding of this specification and the annexed drawings. Thedisclosure includes all such modifications and alterations and islimited only by the scope of the following claims. In particular regardto the various functions performed by the above described components(e.g., elements, resources, etc.), the terms used to describe suchcomponents are intended to correspond, unless otherwise indicated, toany component which performs the specified function of the describedcomponent (e.g., that is functionally equivalent), even though notstructurally equivalent to the disclosed structure which performs thefunction in the herein illustrated exemplary implementations of thedisclosure. In addition, while a particular feature of the disclosuremay have been disclosed with respect to only one of severalimplementations, such feature may be combined with one or more otherfeatures of the other implementations as may be desired and advantageousfor any given or particular application. Furthermore, to the extent thatthe terms “includes”, “having”, “has”, “with”, or variants thereof areused in either the detailed description or the claims, such terms areintended to be inclusive in a manner similar to the term “comprising.”

What is claimed is:
 1. A method, comprising: defining a message behaviorprofile for a sender, the message behavior profile comprising: a messageread rate corresponding to a ratio of a number of messages sent by thesender relative to a number of the messages read by recipients; amessage response rate corresponding to a number of recipients thatrespond to one or more messages sent by the sender; and a messagedistribution pattern corresponding to a number of messages sent by thesender to multiple recipients.
 2. The method of claim 1, comprisingassociating the sender with an IP address and categorizing a messagefrom the IP address based upon the message behavior profile.
 3. Themethod of claim 1, comprising associating the sender with a domain andcategorizing a message from the domain based upon the message behaviorprofile.
 4. The method of claim 1, comprising associating the senderwith an email address and categorizing a message from the email addressbased upon the message behavior profile.
 5. The method of claim 1,comprising associating the sender with a user account and categorizing amessage from the user account based upon the message behavior profile.6. The method of claim 1, comprising associating the sender with adigital certificate and categorizing a message associated with thedigital certificate based upon the message behavior profile.
 7. Themethod of claim 1, comprising associating the sender with a phone numberand categorizing a message from the phone number based upon the messagebehavior profile.
 8. A system, comprising: one or more processing units;and memory comprising instructions that when executed by at least one ofthe one or more processing units perform a method comprising:categorizing a message received from a sender based upon a messagebehavior profile associated with the sender, the message behaviorprofile comprising: a message read rate corresponding to a ratio of anumber of messages sent by the sender relative to a number of themessages read by recipients; a message response rate corresponding to anumber of recipients that respond to one or more messages sent by thesender; and a message distribution pattern corresponding to a number ofmessages sent by the sender to multiple recipients.
 9. The system ofclaim 8, the method comprising identifying the sender based upon an IPaddress.
 10. The system of claim 8, the method comprising identifyingthe sender based upon a domain.
 11. The system of claim 8, the methodcomprising identifying the sender based upon an email address.
 12. Thesystem of claim 8, the method comprising identifying the sender basedupon a user account.
 13. The system of claim 8, the method comprisingidentifying the sender based upon a digital certificate.
 14. The systemof claim 8, the method comprising identifying the sender based upon aphone number.
 15. A computer readable device comprising instructionsthat when executed perform a method, comprising: defining a messagebehavior profile for a sender, the message behavior profile comprisingat least one of: a message read rate corresponding to a ratio of anumber of messages sent by the sender relative to a number of themessages read by recipients; a message response rate corresponding to anumber of recipients that respond to one or more messages sent by thesender; or a message distribution pattern corresponding to a number ofmessages sent by the sender to multiple recipients.
 16. The computerreadable device of claim 15, the method comprising associating thesender with an IP address and categorizing a message from the IP addressbased upon the message behavior profile.
 17. The computer readabledevice of claim 15, the method comprising associating the sender with adomain and categorizing a message from the domain based upon the messagebehavior profile.
 18. The computer readable device of claim 15, themethod comprising associating the sender with an email address andcategorizing a message from the email address based upon the messagebehavior profile.
 19. The computer readable device of claim 15, themethod comprising associating the sender with a user account andcategorizing a message from the user account based upon the messagebehavior profile.
 20. The computer readable device of claim 15, themethod comprising associating the sender with a digital certificate andcategorizing a message associated with the digital certificate basedupon the message behavior profile.